Safe Zones in Tracking Device Environments

ABSTRACT

A tracking system determines if a tracking device is located within a safe zone based on whether a set of safe conditions are satisfied. The set of safe conditions includes a geographic boundary or a geographic location and corresponding threshold distance. The set of safe conditions can also include a time window during which a safe zone is active. When a tracking device is within a safe zone (e.g., geographically and temporally), the tracking device is determined to be safe, and notifications associated with the tracking device can be minimized. The safe zones may be user-selected, user-defined, or determined based on data analytics. If a set of safe conditions are not satisfied, the tracking system generates and sends a notification to the user of the tracking device indicating that the tracking device may be lost.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 16/208,565, filed Dec. 4, 2018 which is a continuation of U.S. application Ser. No. 15/887,274, filed Feb. 2, 2018, now U.S. Pat. No. 10,176,699, which application is a continuation of U.S. application Ser. No. 15/387,243, filed Dec. 21, 2016, now U.S. Pat. No. 9,922,531 all of which are incorporated by reference in their entirety.

BACKGROUND

This disclosure relates generally to tracking devices, and more specifically, to using locations known to a user to improve user experience with tracking devices.

Electronic tracking devices have created numerous ways for people to track the locations of people and/or objects. For example, a user can use GPS technology to track a device remotely or determine a location of the user. In another example, a user can attach a tracking device to an important object, such as keys or a wallet, to more quickly locate the object (e.g., if it becomes lost).

However, if a person or object is located in a safe zone (a location where, even if a tracking device is outside of the communicative range of a mobile device or a user, the tracking device is not considered “lost”), users can be informed that a corresponding tracking device is located within the safe zone. In such instances, a user may wish to minimize the number of notifications or messages presented to the user about the tracking device, thereby improve the user's experience with the tracking device.

SUMMARY

A tracking system determines whether a tracking device is located within a safe zone based on whether the tracking device satisfies a set of safe conditions. In some embodiments, the set of safe conditions can be user-selected or user-defined, while in other embodiments, the set of safe conditions can be determined based on data analytics. If the tracking device is in a safe zone (or “safe” hereinafter), the tracking system may deprioritize, reduce, or disable notifications for the tracking device to the user. If the tracking device is determined to potentially be lost, and is determined to not be safe, the tracking system generates and sends a notification to the user of the tracking device indicating that the tracking device may be lost.

One safe condition can be the location of the tracking device within one or more safe zones. A safe zone may be fixed (e.g., inside a building or within a threshold distance of a landmark), and can include one or more of a geographic location or boundary, a threshold distance from the geographic location or boundary, and a time window. Alternatively, a safe zone may be mobile (e.g., a vehicle) and can include a container object. When a tracking device is within a safe zone (e.g., geographically and/or temporally) the tracking device is determined to be safe. The set of safe conditions may be specific to each tracking device. A user can enable or disable safe conditions for each tracking device.

In one embodiment, a safe zone or tracking device may be associated with an extension time period and an extension distance. The tracking device is safe if the tracking device is within an extension distance away from the safe zone or if the tracking device leaves the safe zone, but returns to the safe zone within the extension time period.

In one embodiment, a safe zone or tracking device may be associated with a delay time. As used herein, a “delay time” refers to an amount of time after a tracking device leaves a safe zone before a user is notified that the tracking device may be lost or has left the safe zone. The delay time may be based on the type of tracking device and its importance to the user. For example, objects of more importance may be associated with shorter delay times and vice versa. In some embodiments, the delay time is based on distance of the tracking device from a safe zone, an amount of time the tracking device is outside of a safe zone, or some combination thereof.

The tracking system may generate and display (for instance, on a display of a client device) a user interface displaying a status of a tracking device including an icon and/or color, wherein the icon or color is based on whether the tracking device satisfies one or more safe conditions. In one embodiment, the tracking system displays all tracking devices via a user interface to the user, and can display a first icon or color for tracking devices determined to be located in safe zones and a second icon or color for tracking devices determined to be located outside of safe zones.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example tracking system environment in which a tracking device can operate, according to one embodiment.

FIG. 2 illustrates an example tracking system for use in a tracking system environment, according to one embodiment.

FIG. 3 illustrates an example user mobile device for use in a tracking system environment, according to one embodiment.

FIG. 4 illustrates an example community mobile device for use in a tracking system environment, according to one embodiment.

FIG. 5 illustrates an example tracking device for use in a tracking system environment, according to one embodiment.

FIG. 6 illustrates an example safe zone environment for tracking devices, according to one embodiment.

FIG. 7 illustrates a flowchart of a process for locating a tracking device, according to one embodiment.

The figures depict various embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.

DETAILED DESCRIPTION Environment Overview

Embodiments described herein detail functionality associated with a tracking device. A user can attach a tracking device to or enclose the tracking device within an object, such as a wallet, keys, a car, a bike, a pet, or any other object that the user wants to track. The user can then use a mobile device (e.g., by way of a software application installed on the mobile device) or other device or service to track the tracking device and corresponding object. For example, the mobile device can perform a local search for a tracking device attached to a near-by object. However, in situations where the user is unable to locate the tracking device using their own mobile device (e.g., if the tracking device is beyond a distance within which the mobile device and the tracking device can communicate), the user can leverage the capabilities of a community of users of a tracking device system.

In particular, a tracking system (also referred to herein as a “cloud server” or simply “server”) can maintain user profiles associated with a plurality of users of the tracking device system. The tracking system can associate each user within the system with one or more tracking devices associated the user (e.g., tracking devices that the user has purchased and is using to track objects owned by the user). If the user's object becomes lost or stolen, the user can send an indication that the tracking device is lost to the tracking system, which is in communication with one or more mobile devices associated with the community of users in communication with the system. The tracking system can set a flag indicating the tracking device is lost. When one of a community of mobile devices that are scanning for nearby tracking devices and providing updated locations to the tracking system identifies a flagged tracking device, the tracking system can associate the received location with the flagged tracking device, and relay the location to a user of the tracking device, thereby enabling the user to locate the lost tracking device.

FIG. 1 illustrates an example tracking system environment in which a tracking device can operate, according to one embodiment. The environment of FIG. 1 includes a tracking system 100 communicatively coupled to a mobile device 102 associated with the user 103 via a first network 108. The tracking system 100 is also communicatively coupled to a plurality of community mobile devices 104 a through 104 n (collectively referred to herein as “community mobile devices 104”) associated with a plurality of users 105 a through 105 n of the tracking system 100 (collectively referred to herein as “community users 105”) via the first network 108. As will be explained in more detail below, the tracking system 100 can allow the user 103 to manage and/or locate a tracking device 106 associated with the user 103. In some embodiments, the tracking system 100 leverages the capabilities of community mobile devices 104 to locate the tracking device 106 if the location of the tracking device is unknown to the user 103 and beyond the capabilities of mobile device 102 to track. In some configurations, the user 103 may own and register multiple tracking devices 106. Although FIG. 1 illustrates a particular arrangement of the tracking system 100, mobile device 102, community mobile devices 104, and tracking device 106, various additional arrangements are possible.

In some configurations, the user 103 may be part of the community of users 105. Further, one or more users 105 may own and register one or more tracking devices 106. Thus, any one of the users within the community of users 105 can communicate with tracking system 100 and leverage the capabilities of the community of users 105 in addition to the user 103 to locate a tracking device 106 that has been lost.

The tracking system 100, mobile device 102, and plurality of community mobile devices 104 may communicate using any communication platforms and technologies suitable for transporting data and/or communication signals, including known communication technologies, devices, media, and protocols supportive of remote data communications.

In certain embodiments, the tracking system 100, mobile device 102, and community mobile devices 104 may communicate via a network 108, which may include one or more networks, including, but not limited to, wireless networks (e.g., wireless communication networks), mobile telephone networks (e.g., cellular telephone networks), closed communication networks, open communication networks, satellite networks, navigation networks, broadband networks, narrowband networks, the Internet, local area networks, and any other networks capable of carrying data and/or communications signals between the tracking system 100, mobile device 102, and community mobile devices 104. The mobile device 102 and community of mobile devices 104 may also be in communication with a tracking device 106 via a second network 110. The second network 110 may be a similar or different type of network as the first network 108. In some embodiments, the second network 110 comprises a wireless network with a limited communication range, such as a Bluetooth or Bluetooth Low Energy (BLE) wireless network. In some configurations, the second network 110 is a point-to-point network including the tracking device 106 and one or more mobile devices that fall within a proximity of the tracking device 106. In such embodiments, the mobile device 102 and community mobile devices 104 may only be able to communicate with the tracking device 106 if they are within a close proximity to the tracking device, though in other embodiments, the tracking device can use long-distance communication functionality (for instance, a GSM transceiver) to communicate with either a mobile device 102/104 or the tracking system 100 at any distance. In some configurations, the mobile device 102 and one or more community mobile devices 104 may each be associated with multiple tracking devices associated with various users.

As mentioned above, FIG. 1 illustrates the mobile device 102 associated with the user 103. The mobile device 102 can be configured to perform one or more functions described herein with respect to locating tracking devices (e.g., tracking device 106). For example, the mobile device 102 can receive input from the user 103 representative of information about the user 103 and information about a tracking device 106. The mobile device 102 may then provide the received user information, tracking device information, and/or information about the mobile device 102 to the tracking system 100. Accordingly, the tracking system 100 is able to associate the mobile device 102, the user 103, and/or the tracking device 106 with one another. In some embodiments, the mobile device 102 can communicate with the tracking device 106 and provide information regarding the location of the tracking device to the user 103. For example, the mobile device 102 can detect a communication signal from the tracking device 106 (e.g., by way of second network 110) as well as a strength of the communication signal or other measure of proximity to determine an approximate distance between the mobile device 102 and the tracking device 106. The mobile device 102 can then provide this information to the user 103 (e.g., by way of one or more graphical user interfaces) to assist the user 103 to locate the tracking device 106. Accordingly, the user 103 can use the mobile device 102 to track and locate the tracking device 106 and a corresponding object associated with the tracking device 106. If the mobile device 102 is located beyond the immediate range of communication with the tracking device 106 (e.g., beyond the second network 110), the mobile device 102 can be configured to send an indication that a tracking device 106 is lost to the tracking system 100, requesting assistance in finding the tracking device. The mobile device 102 can send an indication of a lost device in response to a command from the user 103. For example, once the user 103 has determined that the tracking device 106 is lost, the user can provide user input to the mobile device 102 (e.g., by way of a graphical user interface), requesting that the mobile device 102 send an indication that the tracking device 106 is lost to the tracking system 100. In some examples, the lost indication can include information identifying the user 103 (e.g., name, username, authentication information), information associated with the mobile device 102 (e.g., a mobile phone number), information associated with the tracking device (e.g., a unique tracking device identifier), or a location of the user (e.g., a GPS location of the mobile device 102 at the time the request is sent).

The tracking system 100 can be configured to provide a number of features and services associated with the tracking and management of a plurality of tracking devices and/or users associated with the tracking devices. For example, the tracking system 100 can manage information and/or user profiles associated with user 103 and community users 105. In particular, the tracking system 100 can manage information associated with the tracking device 106 and/or other tracking devices associated with the user 103 and/or the community users 105.

As mentioned above, the tracking system 100 can receive an indication that the tracking device 106 is lost from the mobile device 102. The tracking system 100 can then process the indication in order to help the user 103 find the tracking device 106. For example, the tracking system 100 can leverage the capabilities of the community mobile devices 104 to help find the tracking device 106. In particular, the tracking system 100 may set a flag for a tracking device 106 to indicate that the tracking device 106 lost and monitor communications received from the community mobile devices 104 indicating the location of one or more tracking devices 106 within proximity of the community mobile devices 104. The tracking system 100 can determine whether a specific location is associated with the lost tracking device 106 and provide any location updates associated with the tracking device 106 to the mobile device 102. In one example, the tracking system may receive constant updates of tracking device 106 locations regardless of whether a tracking device 106 is lost and provide a most recent updated location of the tracking device 106 in response to receiving an indication that the tracking device 106 is lost.

In some configurations, the tracking system 100 can send a location request associated with the tracking device 106 to each of the community mobile devices 104. The location request can include any instructions and/or information necessary for the community mobile devices 106 to find the tracking device 102. For example, the location request can include a unique identifier associated with the tracking device 106 that can be used by the community mobile devices 104 to identify the tracking device 106. Accordingly, if one of the community mobile devices 104 detects a communication from the tracking device 106 (e.g., if the community mobile device 104 is within range or moves within range of the communication capabilities of the tracking device 106 and receives a signal from the tracking device 106 including or associated with the unique identifier associated with the tracking device 106), the community mobile device 104 can inform the tracking system 100. Using the information received from the community mobile devices 104, the tracking system 100 can inform the user (e.g., by way of the mobile device 102) of a potential location of the tracking device 106.

As shown in FIG. 1 and as mentioned above, the tracking system 100 can communicate with a plurality of community mobile devices 104 associated with corresponding community users 105. For example, an implementation may include a first community mobile device 104 a associated with a first community user 105 a, a second community mobile device 104 b associated with a second community user 105 b, and additional communication mobile devices associated with additional community users up to an nth community mobile device 104 n associated with an nth community user 105 n. The community mobile devices 104 may also include functionality that enables each community mobile device 104 to identify a tracking device 106 within a proximity of the community mobile device 104. In one example, a first community mobile device 104 a within proximity of a tracking device 106 can communicate with the tracking device 106, identify the tracking device 106 (e.g., using a unique identifier associated with the tracking device 106), and/or detect a location associated with the tracking device 106 (e.g., a location of the first mobile community device 104 a at the time of the communication with the tracking device 106). This information can be used to provide updated locations and/or respond to a location request from the tracking system 100 regarding the tracking device 106. In some embodiments, the steps performed by the first community mobile device 104 a can be hidden from the first community user 105 a. Accordingly, the first community mobile device 104 a can assist in locating the tracking device 106 without bother and without the knowledge of the first community user 105 a.

As mentioned above, the tracking system 100 can assist a user 103 in locating a tracking device 106. The tracking device may be a chip, tile, tag, or other device for housing circuitry and that may be attached to or enclosed within an object such as a wallet, keys, purse, car, or other object that the user 103 may track. Additionally, the tracking device 106 may include a speaker for emitting a sound and/or a transmitter for broadcasting a beacon. In one configuration, the tracking device 106 may periodically transmit a beacon signal that may be detected using a nearby mobile device 102 and/or community mobile device 104. In some configurations, the tracking device 106 broadcasts a beacon at regular intervals (e.g., one second intervals) that may be detected from a nearby mobile device (e.g., community mobile device 104). The strength of the signal emitted from the tracking device 106 may be used to determine a degree of proximity to the mobile device 102 or community mobile device 104 that detects the signal. For example, a higher strength signal would indicate a close proximity between the tracking device 106 and the mobile device 102 and a lower strength signal would indicate a more remote proximity between the tracking device 106 and the mobile device 102, though in some embodiments, the tracking device 106 can intentionally vary the transmission strength of the beacon signal. In some cases, the strength of signal or absence of a signal may be used to indicate that a tracking device 106 is lost.

System Overview

FIG. 2 illustrates an example tracking system for use in a tracking system environment, according to one embodiment. As shown, the tracking system 100 may include, but is not limited to, an association manager 204, a tracking device location manager 206, a tracking device power manager 207, and a data manager 208, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers 204-208 are shown to be separate in FIG. 2, any of the managers 204-208 may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

The association manager 204 may be configured to receive, transmit, obtain, and/or update information about a user 103 and/or information about one or more specific tracking devices (e.g., tracking device 106). In some configurations, the association manager 204 may associate information associated with a user 103 with information associated with a tracking device 106. For example, user information and tracking information may be obtained by way of a mobile device 102, and the association manager 204 may be used to link the user information and tracking information. The association between user 103 and tracking device 106 may be used for authentication purposes, or for storing user information, tracking device information, permissions, or other information about a user 103 and/or tracking device 106 in a database.

The tracking system 100 also includes a tracking device location manager 206. The tracking device location manager 206 may receive and process an indication that the tracking device 106 is lost from a mobile device (e.g., mobile device 102 or community mobile devices 104). For example, the tracking system 100 may receive a lost indication from a mobile device 102 indicating that the tracking device 106 is lost. The tracking device location manager 206 may set a flag on a database (e.g., tracker database 212) indicating that the tracking device 106 is lost. The tracking device location manager 206 may also query a database to determine tracking information corresponding to the associated user 103 and/or tracking device 106. The tracking system 100 may obtain tracking device information and provide the tracking device information or other information associated with the tracking device 106 to a plurality of community mobile devices 104 to be on alert for the lost or unavailable tracking device 106.

The tracking device location manager 206 may also receive a location from one or more community mobile devices 104 that detect the tracking device 106, for instance in response to the community mobile device receiving a beacon signal transmitted by the tracking device 106, without the tracking device 106 having been previously marked as lost. In such embodiments, a user corresponding to the mobile device 102 can request a most recent location associated with the tracking device from the tracking system 100, and the location manager 206 can provide the location received from the community mobile device for display by the mobile device 102. In some embodiments, the location manager 206 provides the location of the tracking device 106 received from a community mobile device either automatically (for instance if the tracking device 106 is marked as lost) or at the request of a user of the mobile device 102 (for instance, via an application on the mobile device 102). The location manager 206 can provide a location of a tracking device 106 to a mobile device 102 via a text message, push notification, application notification, automated voice message, or any other suitable form of communication.

The tracking device location manager 206 may further manage providing indications about whether a tracking device 106 is lost or no longer lost. For example, as discussed above, the tracking device location manager 206 may provide a location request to the community of mobile devices 104 indicating that a tracking device 106 is lost. Additionally, upon location of the tracking device 106 by the user 103 or by one of the community of users 105, the tracking device location manager 206 may provide an indication to the user 103, community user 105, or tracking system 100 that the tracking device 106 has been found, thus removing any flags associated with a tracking device and/or canceling any location request previously provided to the community of users 105. For example, where a user 103 sends an indication that the tracking device 106 is lost to the tracking system 100 and later finds the tracking device 106, the mobile device 102 may provide an indication to the tracking system 100 that the tracking device 106 has been found. In response, the tracking device location manager 206 may remove a flag indicating that the tracking device 106 is lost and/or provide an updated indication to the community of users 105 that the tracking device 106 has been found, thus canceling any instructions associated with the previously provided location request. In some configurations, the notification that the tracking device 106 has been found may be provided automatically upon the mobile device 102 detecting the tracking device 106 within a proximity of the mobile device 102. Alternatively, the notification that the tracking device 106 has been found may be provided by the user 103 via user input on the mobile device 102. In another example, a known user (e.g., a friend or family member) with whom the tracking device 106 has been shared may provide an indication that the tracking device 106 has been found.

The tracking system 100 additionally includes a tracking device safe zone manager 207. The tracking device safe zone manager 207 can store and manage safe zones for a tracking device 106 provided by the user 103 or learned by the tracking system 100 (for instance, based on analysis of historical data associated with the tracking device). As noted above, safe zones can be associated with parameters related to location and time. The safe zone manager 207 can store parameters associated with safe zones in the safe zone database 218, described below.

The tracking system 100 additionally includes a data manager 208. The data manager 208 may store and manage information associated with users, mobile devices, tracking devices, permissions, location requests, and other data that may be stored and/or maintained in a database related to performing location services of tracking devices. As shown, the data manager 208 may include, but is not limited to, a user database 210, a tracker database 212, permissions data 214, location request data 216, and safe zone database 218. It will be recognized that although databases and data within the data manager 208 are shown to be separate in FIG. 2, any of the user database 210, tracker database 212, permissions data 214, location request data 216, and safe zone database 218 may be combined in a single database or manager, or divided into more databases or managers as may serve a particular embodiment.

The data manager 208 may include the user database 210. The user database 210 may be used to store data related to various users. For example, the user database 210 may include data about the user 103 as well as data about each user 105 in a community of users 105. The community of users 105 may include any user that has provided user information to the tracking system 100 via a mobile device 102, 104 or other electronic device. The user information may be associated with one or more respective tracking devices 106, or may be stored without an association to a particular tracking device. For example, a community user 105 may provide user information and permit performance of tracking functions on the community mobile device 104 without owning or being associated with a tracking device 106. The user database 210 may also include information about one or more mobile devices or other electronic devices associated with a particular user.

The data manager 208 may also include a tracker database 212. The tracker database 212 may be used to store data related to tracking devices. For example, the tracker database 212 may include tracking data for any tracking device 106 that has been registered with the tracking system 100. Tracking data may include unique tracker identifications (IDs) associated with individual tracking devices 106. Tracker IDs may be associated with a respective user 103. Tracker IDs may also be associated with multiple users. Additionally, the tracker database 212 may include any flags or other indications associated with whether a specific tracking device 106 has been indicated as lost and whether any incoming communications with regard to that tracking device 106 should be processed based on the presence of a flag associated with the tracking device 106.

The data manager 208 may further include permissions data 214 and location request data 216. Permissions data 214 may include levels of permissions associated with a particular user 103 and/or tracking device 106. For example, permissions data 214 may include additional users that have been indicated as sharing a tracking device 106, or who have been given permission to locate or receive a location of a tracking device 106. Location request data 216 may include information related to a location request or a lost indication received from the user 103 via a mobile device 102. The data manager 208 may further include a safe zone database 218. The safe zone database 218 includes a list of safe zones associated with a particular user 103 and/or tracking device 106, for instance a geographic location or boundary associated with a safe zone, a time period for which the safe zone is enabled, an extension time period or extension distance associated with a safe zone, a delay time associated with a safe zone or tracking device, and the like.

FIG. 3 illustrates an example user mobile device for use in a tracking system environment, according to one embodiment. As shown, the mobile device 102 may include, but is not limited to, a user interface manager 302, a location request manager 304, a database manager 306, and a tracking manager 308, each of which may be in communication with one another using any suitable communication technologies. It will be recognized that although managers 302-308 are shown to be separate in FIG. 3, any of the managers 302-308 may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

As will be explained in more detail below, the mobile device 102 includes the user interface manager 302. The user interface manager 302 may facilitate providing the user 103 access to data on a tracking system 100 and/or providing data to the tracking system 100. Further, the user interface manager 302 provides a user interface by which the user 103 may communicate with tracking system 100 and/or tracking device 106 via mobile device 102. For example, the user interface manager 302 can facilitate providing safe zones defined by the user 103 for the tracking device 106 via mobile device 102 to the tracking system 100.

The mobile device 102 may also include a location request manager 304. The location request manager 304 may receive and process a request input to the mobile device 102 to send an indication that a tracking device 106 is lost to a tracking system 100. For example, the user 103 may provide an indication that a tracking device 106 is lost, unreachable, or otherwise unavailable from the mobile device 102 via the user interface manager 302, and the location request manager 304 may process the lost indication and provide any necessary data to the tracking system 100 for processing and relaying a location request to other users 105 over a network 108. In some configurations, an indication that a tracking device 106 is lost is provided via user input. Alternatively, the indication may be transmitted automatically in response to the mobile device 102 determining that a tracking device 106 is lost.

In addition, the location request manager 304 can request a location of the tracking device 106 without the tracking device 106 being identified as lost. For instance, a user can access a tracking device location feature of an application running on the mobile device 102 (for example, via the user interface manager 302), and the location request manager 304 can request a most recent location of the tracking device 106 from the tracking system 100. The location request manager 304 can receive the most recent location from the tracking system 100, and can display the most recent location via the user interface manager 302.

The mobile device 102 may also include a database manager 306. The database manager 306 may maintain data related to the user 103, tracking device 106, permissions, or other data that may be used for locating a tracking device 106 and/or providing a request to a tracking system 100 for locating one or more tracking devices 106 associated with the user 103. Further, the database manager 306 may maintain any information that may be accessed using any other manager on the mobile device 102.

The mobile device 102 may further include a tracking manager 308. The tracking manager 308 may include a tracking application (e.g., a software application) for communicating with and locating a tracking device 106 associated with the user 103. For example, the tracking manager 308 may be one configuration of a tracking application installed on the mobile device 102 that provides the functionality for locating a tracking device 106 and/or requesting location of a tracking device 106 using a tracking system 100 and/or a plurality of community mobile devices 104. As shown, the tracking manager 308 may include, but is not limited to, a Bluetooth Low Energy (BLE) manager 310, a persistence manager 312, a local files manager 314, a motion manager 316, a secure storage manager 318, a settings manager 320, a location manager 322, a network manager 324, a notification manager 326, a sound manager 328, a friends manager 330, a photo manager 332, an authentication manager 334, and a device manager 336. Thus, the tracking manager 308 may perform any of the functions associated with managers 310-338, described in additional detail below.

The BLE manager 310 may be used to manage communication with one or more tracking devices 106. The persistence manager 312 may be used to store logical schema information that is relevant to the tracking manager 308. The local files manager 314 may be responsible for managing all files that are input or output from the mobile device 102. The motion manager 316 may be responsible for all motion management required by the tracking manager 308. The secure storage manager 318 may be responsible for storage of secure data, including information such as passwords and private data that would be accessed through this sub-system. The settings manager 320 may be responsible for managing settings used by the tracking manager 308. Such settings may be user controlled (e.g., user settings) or defined by the tracking manager 308 for internal use (e.g., application settings) by a mobile device 102 and/or the tracking system 100. The location manager 322 may be responsible for all location tracking done by the tracking manager 308. For example, the location manager 322 may manage access to the location services of the mobile device 102 and works in conjunction with other managers to persist data. The network manager 324 may be responsible for all Internet communications from the tracking manager 308. For example, the network manager 324 may mediate all Internet API calls for the tracking manager 308. The notification manager 326 may be responsible for managing local and push notifications required by the tracking manager 308. The sound manager 328 may be responsible for playback of audio cues by the tracking manager 308. The friends manager 330 may be responsible for managing access to contacts and the user's social graph. The photo manager 332 may be responsible for capturing and managing photos used by the tracking manager 308. The authentication manager 334 may be responsible for handling the authentication (e.g., sign in or login) of users. The authentication manager 334 may also include registration (e.g., sign up) functionality. The authentication manager 334 further coordinates with other managers to achieve registration functionality. The device manager 336 may be responsible for managing the devices discovered by the tracking manager 308. The device manager 336 may further store and/or maintain the logic for algorithms related to device discovery and update.

FIG. 4 illustrates an example community mobile device for use in a tracking system environment, according to one embodiment. As shown, the community mobile device 104 may include, but is not limited to, a user interface manager 402, a tracking device manager 404, a database manager 406, and a tracking manager 408, each of which may be in communication with one another using any suitable communication technologies. The user interface manager 402, database manager 406, and tracking manager 408 illustrated in FIG. 4 may include similar features and functionality as the user interface manager 302, database manager 306, and tracking manager 308 described above in connection with FIG. 3. It will be recognized that although managers 402-408 are shown to be separate in FIG. 4, any of the managers 402-408 may be combined into fewer managers, such as into a single manager, or divided into more managers as may serve a particular embodiment.

The community mobile device 104 may include a tracking device manager 404. The tracking device manager 404 may facilitate scanning for nearby tracking devices 106. In some configurations, the tracking device manager 404 can continuously or periodically scan (e.g., once per second) for nearby tracking devices 106. The tracking device manager 404 may determine whether to provide an updated location of the nearby tracking device 106 to the tracking system 100. In some configurations, the tracking device manager 404 provides a location of a nearby tracking device 106 automatically. Alternatively, the tracking device manager 404 may determine whether the location of the tracking device 106 has been recently updated, and may determine whether to provide an updated location based on the last time a location of the tracking device 106 has been updated (e.g., by the community mobile device 104). For example, where the community mobile device 104 has provided a recent update of the location of a tracking device 106, the tracking device manager 404 may decide to wait a predetermined period of time (e.g., 5 minutes) before providing an updated location of the same tracking device 106.

In one configuration, the tracking device manager 404 may receive and process a location request or other information relayed to the community mobile device 104 by the tracking system 100. For example, the tracking device manager 404 may receive an indication of a tracking device 106 that has been indicated as lost, and provide a location of the tracking device 106 if it comes within proximity of the community mobile device 104. In some configurations, the community mobile device 104 is constantly scanning nearby areas to determine if there is a tracking device 106 within a proximity of the community mobile device 104. Therefore, where a tracking device 106 that matches information provided by the tracking system 100 (e.g., from the location request) comes within proximity of the community mobile device 104, the tracking device manager 404 may generate and transmit a response to the location request to the tracking system 100, which may be provided to the user 103 associated with the tracking device 106. Further, generating and transmitting the response to the tracking request may be conditioned on the status of the tracking device 106 being flagged as lost by the mobile device 102 and/or the tracking system 100.

The tracking device manager 404 may additionally provide other information to the tracking system 100 in response to receiving the tracking request. For example, in addition to providing a location of the community mobile device 104, the tracking device manager may provide a signal strength associated with the location to indicate a level of proximity to the location of the community mobile device 104 provided to the user 103. For example, if a signal strength is high, the location provided to the user 103 is likely to be more accurate than a location accompanied by a low signal strength. This may provide additional information that the user 103 may find useful in determining the precise location of tracking device 106.

As described above, the tracking device manager 404 may determine whether to send a location within the proximity of the tracking device 106 to the tracking system 100. The determination of whether to send a location to the tracking system 100 may be based on a variety of factors. For example, a tracking device manager 404 may determine to send a location of the tracking device 106 to a tracking system 100 based on whether the detected tracking device 106 has been indicated as lost or if a tracking request has been provided to the community mobile device 104 for the particular tracking device 106. In some configurations, the community mobile device 104 may send an update of a location of a tracking device 106 even if the tracking device 106 is not associated with a current tracking request or if the tracking device 106 is not indicated as lost. For example, where the location of a tracking device 106 has not been updated for a predetermined period of time, the community mobile device 104 may provide an update of a tracking device location to the tracking system 100, regardless of whether a tracking request has been received.

In some configurations, the community mobile device 104 may include additional features. For example, the community mobile device 104 may allow a tracking system 100 to snap and download a photo using photo functionality of the community mobile device 104. In some configurations, this may be an opt-in feature by which a community user 105 permits a tracking system 100 to take a snap-shot and possibly provide a visual image of an area within a proximity of the tracking device 106.

FIG. 5 illustrates an example tracking device for use in a tracking system environment, according to one embodiment. The tracking device 106 of FIG. 5 includes an interface 502, a transceiver 504, a controller 506, one or more sensors 508, and a GPS unit 510. The transceiver 504 is a hardware circuit capable of both transmitting and receiving signals. It should be noted that in other embodiments, the tracking device 106 includes fewer, additional, or different components than those illustrated in FIG. 5. For instance, in some embodiments, the tracking device 106 does not include a GPS unit 510.

The interface 502 provides a communicative interface between the tracking device 106 and one or more other devices, such as a mobile device 102. For instance, the interface 502 can instruct the transceiver 504 to output beacon signals as described above (for example, periodically or in response to a triggering event, such as a detected movement of the tracking device 106). The interface 502 can, in response to the receiving of signals by the transceiver 504 from, for instance, the mobile device 102, manage a pairing protocol to establish a communicative connection between the tracking device 106 and the mobile device 102. As noted above, the transceiver 504 can include a BLE receiver and transmitter, though in other embodiments, the transceiver 504 enables communications via other suitable wireless connection protocols (such as WiFi, Global System for Mobile Communications or “GSM”, LTE, and the like). It should be noted that while various examples herein describe the transceiver 504 as a GSM receiver and transmitter, this is done for the purposes of brevity, and it should be emphasized that the transceiver 504 can communicate over any other available wireless communication protocol according to the embodiments described herein.

The controller 506 is a hardware chip that configures the tracking device 106 to perform one or more functions or to operate in one or operating modes or states. For instance, the controller 506 can configure the interval at which the transceiver broadcasts beacon signals, can authorize or prevent particular devices from pairing with the tracking device 106 based on information received from the devices and permissions stored at the tracking device, can increase or decrease the transmission strength of signals broadcasted by the transceiver, can configure the interface to emit a ringtone or flash an LED light, can enable or disable various tracking device sensors, can enable or disable a tracking device GPS unit, can enable or disable communicative functionality of the tracking device 106 (such as a GSM transmitter and receiver), can configure the tracking device into a sleep mode or awake mode, can configure the tracking device into a power preservation mode, and the like. The controller 506 can configure the tracking device to perform functions or to operate in a particular operating mode based on information or signals received from a device paired with or attempting to pair with the tracking device 106, based on an operating state or connection state of the tracking device 106, based on user-selected settings, based on information stored at the tracking device 106, based on a detected location of the tracking device 106, based on historical behavior of the tracking device 106 (such as a previous length of time the tracking device was configured to operate in a particular mode), based on information received from the sensors 508 or the GPS unit 510, or based on any other suitable criteria.

The controller 506 can configure the tracking device 106 to operate in one or more power preservation modes. Each power preservation mode is associated with a set of tracking device settings. For instance, the controller 506 can configure the tracking device 106 to operate according to factory default power saving mode that includes a set of tracking device settings pre-installed on the tracking device. Likewise, the controller 506 may receive a set of tracking device settings associated with a user-defined power preservation mode from a user 103 through the user interface manager 302 of a mobile device 102.

The sensors 508 can include motion sensors (such as gyroscopes or accelerators), altimeters, orientation sensors, proximity sensors, light sensors, or any other suitable sensor configured to detect an environment of the tracking device 106, a state of the tracking device 106, a movement or location of the tracking device 106, and the like. The sensors 508 are configured to provide information detected by the sensors to the controller 506. The GPS unit 510 is configured to detect a location of the tracking device 106 based on received GPS signals, and is configured to provide detected locations to the controller 506.

Tracking Device Safe Zone Overview

A tracking system 100 determines whether a tracking device 106 is safe, and therefore not lost. A tracking device 106 can be determined to be safe if a set of safe conditions is satisfied. In some embodiments, the set of safe conditions can be user-selected or defined, while in other embodiments, the set of safe conditions can be determined based on an analysis of historical location and time data associated with a tracking device. For instance, if a tracking device is historically located within a user's home, or if the tracking device is historically located within a geographic boundary associated with a user's place of work during the hours of 9 am to 5 pm, a safe zone can be automatically defined by the tracking system 100 for these places and times. In one embodiment, a safe zone can be determined based on a probability that a tracking device is in a given location at a certain time. The tracking device 106 may be determined to be safe if the probability is higher than a threshold probability, which can be selected by the user or automatically defined by the tracking system 100. Continuing with a previous example, if the tracking device 106 is located within a geographic boundary associated with the user's place of work during work the work hours of 9 am to 5 pm and the user sets a safe zone threshold probability to 85%, the tracking device 106 is considered safe if the probability that the tracking device is located within the geographic boundary is greater than 85%. The tracking device 106 may have a lower probability of being in a given location at a certain time the greater the distance from the given location and the greater the difference in time from a time that is considered safe. If the tracking device 106 is determined to be safe, the tracking system 100 may deprioritize, reduce, disable, or prevent notifications generated by the tracking system 100 from being sent to the user. If the tracking device 106 is not safe, the tracking system 100 generates and sends a notification to the user 103 of the tracking device 106 indicating that the tracking device may be lost.

The set of safe conditions can include definitions for one or more safe zones. A safe zone may be fixed (e.g., building or landmark), and can include a defined geographic boundary, or a geographic location and corresponding threshold distance (e.g., the safe zone includes all locations within the threshold distance of the geographic location). Alternatively, a safe zone may be mobile and can include a container object (such as a vehicle). A safe zone can be defined based on the presence of two or more tracking devices being located in the same place at the same time. A safe zone may be active or enabled only during a particular time period (e.g., work hours on weekdays, between 5 pm and 10 pm on weekends, etc.). When a tracking device 106 is within a safe zone (e.g., both geographically and temporally), the set of safe conditions defining the safe zone is determined to be satisfied, and the tracking device 106 is determined to be safe. The set of safe conditions may be specific to one or more tracking devices, one or more users, and the like. For instance, each of a user's tracking devices may be associated with different sets of safe conditions, or a set of tracking devices may be associated with the same set of safe conditions.

For a safe zone associated with a fixed geographic boundary or location, if the location of a tracking device 106 is within the geographic boundary or within a threshold distance of the geographic location, the tracking device 106 is determined to be safe. For a mobile safe zone, if the location of the tracking device 106 is within a threshold distance of the location of the container object associated with the mobile safe zone, the tracking device is determined to be safe. A container object can be an object that can contain (e.g., secure) a tracking device 106 (such as a vehicle), or can be an object that moves in conjunction with the tracking device (such as a bicycle). For example, a tracking device 106 may be placed within a car with GPS capabilities. The GPS of the car can provide the location associated with the car, and a user's mobile device can provide the location of the tracking device 106. If the location of the tracking device 106 is within a threshold distance of the GPS location associated with the car, the tracking device 106 can be determined to be in the car and therefore safe. For a safe zone formed by two tracking devices, a tracking device 106 is determined to be safe if it is within a threshold distance of the location of another tracking device within a certain time. For example, a tracking device could be attached to a boat slip, and the tracking device 106 may be attached to a sailboat. If the tracking device 106 attached to the sailboat is located within the threshold distance of the tracking device attached to the boat slip at a certain time, the tracking device 106 is considered safe. In another example, a tracking device could be attached to or located inside a container object such as a vehicle to help identify the safe zone associated with the vehicle. If the safe zone further comprises a time window, the tracking device 106 must also be within the threshold distance of the geographic location or container object during the associated time window to be determined safe.

A safe zone may be user defined. A user 103 may define one or more safe zones, such as a user's home or office, and can define geographic boundaries or geographic locations and corresponding distances associated with the safe zones. A user 103 can enable or disable safe conditions for a particular tracking device 106. In one embodiment, a user interface manager 302 may allow a user 103 to input a geographic location (e.g., street address or GPS coordinates). The geographic location may be associated with a point location (e.g., approximate or exact GPS coordinates) and/or an area (e.g., default area associated with geographic location, building footprint, or some indication of property boundary), and a default or user-defined threshold distance that defines either a circular area from the point location or a threshold distance from the perimeter of the area associated with the geographic location. Alternatively, the safe zone may be defined as a geographic boundary. For example, a user interface manager 302 may allow a user 103 to input one or more geographic locations to define a geographic boundary of a safe zone. Additionally, the user interface manager 302 may allow a user to specify a time window associated with each safe zone.

Alternatively, the tracking system 100 may identify one or more candidate safe zones based on historical time and location data of a tracking device 106. For example, a first candidate safe zone can be identified based on historical location data of the tracking device 106 from 10 PM to 6 AM (e.g., within the user's home) and a second candidate safe zone can be identified based on historical location data of the tracking device 106 from 8 AM to 5 PM on weekdays (e.g., within the user's office). The tracking system 100 can present identified candidate safe zones to a user, and the user can select one or more of the candidate safe zones for use in determining whether a tracking device is safe. Alternatively, the tracking system 100 can apply candidate safe zones for use in determining whether a tracking device is safe without explicit authorization from the user.

In one embodiment, when a tracking device 106 is determined to be lost, the tracking system 100 sends a silent push notification to a client device to wake up and scan for the tracking device 106. The tracking system 100 may use modeling techniques such as ensemble modeling with safe zones to determine whether the tracking device 106 is lost and whether to scan for it. For example, the tracking system 100 may determine that the client device is located in a safe zone for the tracking device 106 and will not send a silent push notification to the client device because the probability that the tracking device 106 is in the safe zone is either reduced or zero. Battery consumption can be reduced for the client device by the tracking system 100 by not sending a silent push notification to the client device to wake up and scan for the tracking device 106.

The tracking system 100 informs the user 103 when a tracking device 106 is determined to be lost. However, it is undesirable to unnecessarily inform the user that a tracking device 106 may be lost when the tracking device 106 is not in fact lost. In one embodiment, a safe zone or tracking device is associated with an extension time period and an extension distance (for instance, a default or user-defined extension time period and extension distance). When the tracking device 106 leaves the safe zone, the tracking device 106 may trigger a timer. The timer counts the amount of time the tracking device 106 is outside the safe zone. If the timer exceeds the extension time period (i.e., the tracking device 106 does not return to a safe zone within the extension time period, such as 30 seconds or 60 seconds), a notification may be sent to the user that the tracking device 106 may be lost. Likewise, when the tracking device 106 leaves the safe zone, a notification can be sent to the user that the tracking device 106 may be lost if the tracking device 106 moves more than the extension distance away from the safe zone. In one embodiment, a safe zone or tracking device 106 is associated with a delay time (for instance, a default or user-defined delay time). The delay time may be based on the type of tracking device and its importance to the user. For example, objects of greater importance may have shorter delay time. The delay time may be based on a distance of the tracking device 106 from a safe zone, an amount of time the tracking device 106 has been outside the safe zone, or some combination thereof. For example, greater distances away from the safe zone may be associated with shorter delay times, and vice versa. The tracking system 100 sends a notification to the user that the tracking device 106 may be lost after the delay time has elapsed.

FIG. 6 illustrates an example safe zone environment for tracking devices, according to one embodiment. The tracking device 614 (e.g., attached to a user's passport) is located within safe zone 612 associated with a user's home 610. The safe zone 612 is a fixed circular safe zone associated with a geographic location and corresponding threshold distance from the geographic location. The tracking device 634 (e.g., attached to a user's keys) is located within a mobile safe zone 626 of a user's vehicle 630. The tracking device 624 is located within the fixed safe zone 622 of parking lot 620 which is outside the mobile safe zone 626 of a user's vehicle 630. The tracking device 624 (e.g., attached to a user's keys) may be determined to be lost if outside of a time period associated with the safe zone (e.g., a time during which the user has left the parking lot 620 and has entered the office 640). Alternatively, if the tracking device 624 is attached to a user's bike, the tracking device 624 may be determined to be safe if located within the safe zone 622 of the parking lot 620 during normal work hours. The tracking device 644 (e.g., attached to a user's briefcase) is within safe zone 642 of the office 640. Tracking device 654 (e.g., attached to a user's wallet) is outside any safe zone, and is determined to be lost. Although not shown, each safe zone may also have an associated time window. For example, tracking device 624 (e.g., attached to a user's bike) may be determined to be safe only during the hours of 8 AM and 5 PM in the safe zone 622 of the parking lot 620. If the tracking device 624 is found in safe zone 622 outside the hours of 8 AM to 5 PM, the bike is considered not safe and thus potentially lost.

FIG. 7 illustrates a flowchart of a process for locating a tracking device, according to one embodiment. Alternate embodiments may contain more, fewer, or different steps, or the steps may be performed in an order different from the order shown in FIG. 7.

The tracking system 100 receives 700 a location of a tracking device and a time associated with the received location (e.g., a time that the location of the tracking device was determined). The tracking system 100 determines 710 if the tracking device satisfies a set of safe conditions based on the location of the tracking device. In some embodiments, determining if the tracking device satisfies the set of safe conditions is further based on the received time. If the set of safe conditions is satisfied, the tracking system 100 can identify the tracking device as safe and thus 715 deprioritizes, reduces, disables, or prevents notifications about the status of the tracking device from being sent to a user's mobile device. If the set of safe conditions are not satisfied, the tracking system 100 determines that the tracking device is outside of a safe zone and identifies 720 the tracking device as potentially lost. The tracking system 100 generates 730 a notification identifying the tracking device and indicating that the tracking device is potentially lost, and provides 740 the generated notification to the user's mobile device. In some embodiments, the notification includes the received location of the tracking device.

The tracking system 100 may generate a user interface for display by a client device, including a representation whether a tracking device 106 is located in a safe zone. The representation can include an icon and/or color based on whether the tracking device satisfies a set of safe conditions (e.g., a first icon and/or color associated with a tracking device satisfying the set of safe conditions, a second icon and/or color associated with a tracking device not satisfying the set of safe conditions, a third icon and/or color associated with a tracking device being outside of a safe zone but for less than an amount of time equal to an extension time, etc.). In one embodiment, the user interface manager 302 may display a safe zone status for all tracking devices of a user on the mobile device 102. The colors or icons included within a user interface can also vary based on a type of tracking device and/or safety zone associated with the tracking device (e.g., a “home” icon for tracking devices at home, a “work” icon for tracking devices work, etc).

Additional Considerations

The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

Any of the devices or systems described herein can be implemented by one or more computing devices. A computing device can include a processor, a memory, a storage device, an I/O interface, and a communication interface, which may be communicatively coupled by way of communication infrastructure. Additional or alternative components may be used in other embodiments. In particular embodiments, a processor includes hardware for executing computer program instructions by retrieving the instructions from an internal register, an internal cache, or other memory or storage device, and decoding and executing them. The memory can be used for storing data or instructions for execution by the processor. The memory can be any suitable storage mechanism, such as RAM, ROM, flash memory, solid state memory, and the like. The storage device can store data or computer instructions, and can include a hard disk drive, flash memory, an optical disc, or any other suitable storage device. The I/O interface allows a user to interact with the computing device, and can include a mouse, keypad, keyboard, touch screen interface, and the like. The communication interface can include hardware, software, or a combination of both, and can provide one or more interfaces for communication with other devices or entities.

Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules, without loss of generality. The described operations and their associated modules may be embodied in software, firmware, hardware, or any combinations thereof.

Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product comprising a computer-readable medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, and/or it may comprise a general-purpose computing device selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a non-transitory, tangible computer readable storage medium, or any type of media suitable for storing electronic instructions, which may be coupled to a computer system bus. Furthermore, any computing systems referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.

Embodiments of the invention may also relate to a product that is produced by a computing process described herein. Such a product may comprise information resulting from a computing process, where the information is stored on a non-transitory, tangible computer readable storage medium and may include any embodiment of a computer program product or other data combination described herein.

Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims. 

What is claimed is:
 1. A method for locating a tracking device of a user, comprising: receiving, by a tracking system from a first mobile device, a location of the tracking device; determining, by the tracking system, if a set of safe conditions is satisfied based at least in part on whether the location of the tracking device is within a geographic boundary associated with the set of safe conditions; and in response to determining that the set of safe conditions are satisfied: identifying, by the tracking system, one or more notifications generated in response to one or more lost conditions being satisfied and indicating that the tracking device may be lost; and decreasing, by the tracking system, a frequency that the identified notifications are sent to a second mobile device of the user.
 2. The method of claim 1, wherein decreasing the frequency that the identified notifications are sent to the second mobile device comprises preventing the identified notifications from being set to the second mobile device.
 3. The method of claim 1, wherein the geographic boundary is defined by a threshold distance from a geographic location.
 4. The method of claim 3, wherein the geographic location is based on a location of another tracking device.
 5. The method of claim 1, wherein the set of safe conditions is defined by the user of the tracking device.
 6. The method of claim 1, wherein the set of safe conditions is determined based on historical data associated with the tracking device without input from the user.
 7. The method of claim 1, wherein the second mobile device is configured to generate a user interface, and wherein displaying the notification comprises displaying an indication that the set of safe conditions associated with the tracking device are satisfied.
 8. A tracking system for locating a tracking device of a user, comprising: a processor; and a non-transitory computer-readable storage medium storing executing instructions that, when executed, cause the processor to perform steps comprising: receiving a location of the tracking device; determining if a set of safe conditions is satisfied based at least in part on whether the location of the tracking device is within a geographic boundary associated with the set of safe conditions; and in response to determining that the set of safe conditions are satisfied: identifying one or more notifications generated in response to one or more lost conditions being satisfied and indicating that the tracking device may be lost; and decreasing a frequency that the identified notifications are sent to a second mobile device of the user.
 9. The tracking system of claim 8, wherein decreasing the frequency that the identified notifications are sent to the second mobile device comprises preventing the identified notifications from being set to the second mobile device.
 10. The tracking system of claim 8, wherein the geographic boundary is defined by a threshold distance from a geographic location.
 11. The tracking system of claim 10, wherein the geographic location is based on a location of another tracking device.
 12. The tracking system of claim 8, wherein the set of safe conditions is defined by the user of the tracking device.
 13. The tracking system of claim 8, wherein the set of safe conditions is determined based on historical data associated with the tracking device without input from the user.
 14. The tracking system of claim 8, wherein the second mobile device is configured to generate a user interface, and wherein displaying the notification comprises displaying an indication that the set of safe conditions associated with the tracking device are satisfied.
 15. A non-transitory computer-readable storage medium storing executable computer instructions that, when executed by a hardware processor of a tracking system, cause the hardware processor to perform steps, comprising: receiving, by a tracking system from a first mobile device, a location of the tracking device; determining, by the tracking system, if a set of safe conditions is satisfied based at least in part on whether the location of the tracking device is within a geographic boundary associated with the set of safe conditions; and in response to determining that the set of safe conditions are satisfied: identifying, by the tracking system, one or more notifications generated in response to one or more lost conditions being satisfied and indicating that the tracking device may be lost; and decreasing, by the tracking system, a frequency that the identified notifications are sent to a second mobile device of the user.
 16. The non-transitory computer-readable storage medium of claim 15, wherein decreasing the frequency that the identified notifications are sent to the second mobile device comprises preventing the identified notifications from being set to the second mobile device.
 17. The non-transitory computer-readable storage medium of claim 15, wherein the geographic boundary is defined by a threshold distance from a geographic location.
 18. The non-transitory computer-readable storage medium of claim 17, wherein the geographic location is based on a location of another tracking device.
 19. The non-transitory computer-readable storage medium of claim 15, wherein the set of safe conditions is defined by the user of the tracking device.
 20. The non-transitory computer-readable storage medium of claim 15, wherein the set of safe conditions is determined based on historical data associated with the tracking device without input from the user. 